Class Diagram Restructuring with GROOVE
نویسندگان
چکیده
منابع مشابه
Class Diagram Restructuring with GROOVE
This paper describes the GROOVE solution to the “Class Diagram Restructuring” case study of the Tool Transformation Contest 2013 [4]. GROOVE [5, 2] is designed to support state space exploration and model checking of dynamically evolving systems; however, as we will show in this contribution, it can also be used to demonstrate graph transformations as a basis for model transformation. GROOVE’s ...
متن کاملCase study: Class diagram restructuring
This case study is an update-in-place refactoring transformation on UML class diagrams. Its aim is to remove clones of attributes from a class diagram, and to identify new classes which abstract groups of classes that share common data features. It is used as one of a general collection of transformations (such as the removal of redundant inheritance, or multiple inheritance) which aim to impro...
متن کاملSolving the Class Diagram Restructuring Transformation Case with FunnyQT
FunnyQT is a new model querying and transformation approach which is implemented as an API for the functional, JVM-based Lisp-dialect Clojure. It provides several sub-APIs for implementing different kinds of queries and transformations. For example, there is a model-to-model transformation API, and there is an in-place transformation API for writing programmed graph transformations. FunnyQT cur...
متن کاملA UML Class Diagram Analyzer
Automatic analysis of UML models constrained by OCL invariants is still an open research topic. Especially for critical systems, such tool support is important for early identification of errors in modeling, before functional requirements are implemented. In this paper, we present ideas on an approach for automatic analysis of UML class diagrams, according to a precise semantics based on Alloy,...
متن کاملClustering Class Diagram through Mining
A class diagram models the static view of a system. The class diagrams are widely used during construction of executable code for software application as it is the only UML diagram which can be directly mapped with object oriented language. As class diagram contains duplicacy, the redundant source code generated increases the complexity of the program code. A solution is required to remove the ...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
ژورنال
عنوان ژورنال: Electronic Proceedings in Theoretical Computer Science
سال: 2013
ISSN: 2075-2180
DOI: 10.4204/eptcs.135.10